Conversation
|
Thanks! I was about to send the same PR, just waiting for my rebased branch to build on riscv64-linux. rc2 worked fine so this should be good as well (rc2 is same as the released version). |
trofi
left a comment
There was a problem hiding this comment.
Looks great! Built a few libunwind revdeps locally without any problems.
|
Result of 286 packages marked as broken and skipped:
3 packages blacklisted:
1937 packages failed to build:
4 packages built:
|
Well.... let's hold this for a while. |
Let me know if any build logs would be helpful. |
|
Yeah, looking at the build log would be interesting. We can pick one target as an example, say |
|
For the time being, let's perhaps add |
|
libunwind's API almost did not change. I would be very surprised if this update breaks anything. My suspiction is that most build failures are not directly related to this PR. Core libraries of different versions are a bit hard to mix and match if they can end up in a final binary of both versions. |
|
I am re‐running a few evaluations to find out more. So far I haven’t found one that failed because of libunwind. |
|
I noticed some evaluation failures when running nixpkgs-review, after the rebase it seems to run fine. |
|
Looks like we got two more releases today: https://github.com/libunwind/libunwind/releases |
jonringer
left a comment
There was a problem hiding this comment.
LGTM
can stabilize on staging-next
All patches and riscv64-linux support is now upstream.
Motivation for this change
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)nixos/doc/manual/md-to-db.shto update generated release notes